home *** CD-ROM | disk | FTP | other *** search
- Subject: Re: Digested
- Date: Mon, 01 Aug 1994 12:24:21 +1000
- From: Warwick Allison <warwick@cs.uq.oz.au>
- Precedence: bulk
-
- Evan K. Langlois wrote:
- >file Filename in ascii, extension gives clue to type. (full path only?)
- >
- >Hmm .. I don't think a full path is needed. Applications shouldn't
- >change from the working directory so making things relative to that
- >shouldn't be too hard.
-
- The problem would be that an app_defs.sys editor wouldn't know where the
- application was, so couldn't use the file selector. So I guess the user
- _could_ use relative paths, but the editor would provide no assistance.
-
- >Looks fine to me. Does the code you posted (it was you right, Warwick?)
- >handle the dot in the center of the attribute properly?
-
- No, the 5-line pattern-matcher I posted was a pure wildcard string match,
- regardless of any special consideration. It was just an example code, and
- in reality, I think a TSR would be the way to go. That way, we completely
- shield the application from knowing where the app_defs file is, and even what
- exact format it is in. The TSR would just do the attribute->value magic for
- the application. It could even implement the text-value->value mapping
- (eg. deciding how to convert "<Ctrl>A" into a scancode).
-
- >========================================================================
- >The correct way to track every mouse movement is to watch a 1x1 pixel
- >rectangle. ...
- >========================================================================
- >
- >I like a snapped 8x8 rectangle. Less events, faster drawing (usually)
-
- Actually, it doesn't make any difference. If you wait on a 1x1 rectangle,
- you don't get every single pixel position as the mouse moves, only as many
- as your program manages to keep up with.
-
- --
- Warwick
-